SYMANTEC--PETER NORTON GROUP README.TXT--April 19, 1994 Copyright 1994 Symantec Corp. All Rights Reserved. NORTON UTILITIES ADMINISTRATOR Version 1.0 Welcome to the Norton Utilities Administrator! Please read this document carefully; it contains important information not included in the user's guide. This document and the on-line help have the latest and most accurate information. For easiest reading, MAXIMIZE this window by clicking the Maximize button. You may also want to print it for future reference. If you still have questions after reviewing this Readme file, call Technical Support for assistance. --------------------------------------------------- CONTENTS --------------------------------------------------- 1. SWAPPER TECHNOLOGY 1.1 What is it? 1.2 Non-Swapping Agents 1.3 When is it useful? 1.4 Additional Switches 2. LIMITATIONS OF THE AGENTS 2.1 Minimum Memory Requirement to run each Agent 3. DISK DOCTOR AGENT 3.1 Undo Files 3.2 Compressed Drives 3.3 Unsupported Drive Types 4. RESCUE AGENT 4.1 Norton Utilities files needed to make Rescue Disks 4.2 Adding Network Drivers to RESCUE.INI 5. UNINSTALL 5.1 Location of NUA 5.2 The Data Directory 6. NOT FOR RESALE VERSION AND 10 USER PACK 6.1 Ten Record Limitation 7. MISCELLANEOUS 7.1 Problems with Memory Managers 7.2 Problems Detecting the Data Directory =================================================== 1 SWAPPER TECHNOLOGY =================================================== 1.1 What is it? Norton Utilities Administrator (NUA) comes with two versions of each of it's agents. Both versions of the programs are identical, but the default versions have had a special "pre-loader" attached to them. This "pre-loader" is called the Swapper. The Swapper allows the agents to run from a login shell with much less memory than would normally be available. It does this by "swapping" the login shell itself out of conventional memory, executing the agent, then swapping the login shell back into memory. The Agents will automatically choose where to swap. The order of preference is Extended (XMS) memory, Expanded (EMS) memory, then Disk. These defaults can be modified with command line switches. The file names of the Swapping Agents are: NDDNET.EXE NARESCUE.EXE 1.2 Non-Swapping Agents The Swapping Agents may not be of benefit in all network setups. For this reason non-swapping versions of each agent have also been provided. The file names of the Non-Swapping Agents are: NDDNETB.EXE RESCUEB.EXE 1.3 When is it useful? Novell Netware: The swapping agents are most useful in a Novell Netware environment. The best way to run the NUA Agents is directly from the system login script. Without the swapper technology, the memory available for NDD and Rescue to run in would be limited by the 150K overhead of the Netware login shell. With the swapping agents, this 150K overhead is eliminated and the Agents should never face memory limitations. MS Lan Manager and IBM Lan Server: Lan Man and Lan Server run external programs in an unusual manner that limits the full potential of the swapper technology. Instead of swapping out the entire 200K NET shell, only a small 6-10K stub of the command processor will be swapped. Running the agents from a batch file after login (as mentioned in the manual) may be a better solution to low memory conditions in these environments. Banyan Vines and Dec Pathworks: Running the agents from a batch file after login (as mentioned in the manual) may be the best solution to low memory conditions in these environments. 1.4 Additional Switches The following switches are available to control the swapping versions of the agents. /SWAP:n Force Swapping to use the following type of storage Where n is: E for EMS X for XMS D for Disk (/TEMP is also required) /TEMP=dir Where dir is the name of the directory where the temporary swap file will be created. Disk swapping will not occur without the TEMP switch being defined. /SKIPHIGH Do not use upper memory This switch should only be used on the non-swapping agents. /NOEMS Do not use EMS memory /NOXMS Do not use XMS memory /NOFRAME Do not use the EMS Page Frame =================================================== 2 LIMITATIONS OF THE AGENTS =================================================== 2.1 Minimum Memory Requirement to Run Each Agent AGENTS REQUIRED MEMORY NDDNET.EXE 375 KB (swapping version) NARESCUE.EXE 360 KB (swapping version) NDDNETB.EXE 360 KB + Login Shell overhead RESCUEB.EXE 345 KB + Login Shell overhead Please note that if you are running from a login script or shell, you will need additional memory to make up for it's overhead. If you use the swapping versions of the agents, this overhead can often be eliminated. =================================================== 3 DISK DOCTOR AGENT =================================================== 3.1 Undo Files The Disk Doctor agent can be configured to create an Undo File every time a repair is made. The files are stored in a directory off of the DATA directory. (Usually this directory is NADMIN.UTD) Since these files can be quite large, and since UNDO files are only useful if no changes have been made to the repaired disk, they are automatically deleted after 30 days. If an UNDO file exceeds the size of a single floppy disk, the Create Undo Disk option in the NUA Console will not work normally. Instead it will display the full network pathname of the Undo file. Make note of this name. Create a Rescue Disk which will contain Norton Disk Doctor. Run NDD on the workstation with the problem, and choose the UNDO option. The Undo file can then be retrieved directly from the network. 3.2 Compressed Drives Testing the compression structures of a compressed drive (especially very large Stacker volumes) can sometimes be a lengthy process. If a particular workstation experiences excessive delays, try running a defragmentation program such as Norton Speed Disk. Alternatively, the Compression Structure tests for that workstation can be disabled. Norton Utilities Administrator fully supports compressed volumes created with Stacker 2.0, Stacker 3.0, Stacker 3.1, SuperStor 2.0x, SuperStor Pro 1.0x, DR-DOS 6 SuperStor, Novell DOS 7 Stacker, IBM DOS 6.1 SuperStor/DS, and MS-DOS 6.x DoubleSpace. Do not attempt to run the Disk Doctor agent on volumes created with other disk compression utilities. The NUA Disk Doctor Agent does not fully support Stacker 4.0, and will not attempt to test or repair a Stacker 4.0 volume. It is possible to disable testing of the compression structures. This will allow testing and repair of the DOS disk stuctures. Running the surface test on a Stacker 4.0 volume is not recommended. 3.3 Unsupported Drive Types The NUA Disk Doctor Agent will not test floppy drives, removable drives (such as Bernoulli or Sydos), or Ram drives. =================================================== 4 RESCUE AGENT =================================================== 4.1 Norton Utilities files needed to make Rescue Disks When creating a Rescue Disk from the Console, NUA will search for a copy of Norton Utilities. If Norton Utilities is not found in the path, programs such as Norton Disk Doctor, Unerase, and Rescue will not be available on the Rescue Disk. 4.2 Adding Network Drivers to RESCUE.INI It is possible to configure the Rescue Agent to backup the network drivers from each workstation. Since configurations and driver names vary widely, sample sections have been left as comments in the RESCUE.INI file contained in the DATA directory. Review and modify the commented sections in the [NADMIN-SETUP] and [INCLUDE] sections to suit your specific needs. Refer to the manual for more information regarding the RESCUE.INI file. =================================================== 5 UNINSTALL =================================================== 5.1 Location of NUA When the Uninstall program is run, the directories that NUA is to be removed from must be specified manually. Use the browse buttons to select the drive and directories that NUA was installed in. 5.2 The Data Directory When the Uninstall program is complete, some files in the DATA directory may not have been deleted. The file storage directory (usually NADMIN.UTD) and it's contents should be deleted manually. =================================================== 6 NOT FOR RESALE VERSION AND THE 10-USER PACK =================================================== 6.1 Ten Record Limitation The "NFR" version and the 10-user pack of NUA has as built-in limitation of ten records in the database. Once ten workstation records have been added to the database, the Agents will report that they can not run on any additional systems. To upgrade to a version beyond 10 users (either for the NFR or 10-user pack) please contact your Symantec Products representative. =================================================== 7 MISCELLANEOUS =================================================== 7.1 Problems with Memory Managers If your system uses an advanced memory manager such as QEMM, 386Max, or MS-DOS 6.x EMM386, proper configuration can eliminate many problems. Fortunately, these memory managers provide utilities that automatically optimize the memory manager's configuration. Use this optimization program to configure your memory manager for efficient and trouble-free use. The optimizers for each of these memory managers are: QEMM - OPTIMIZE MS-DOS 6.x EMM386 - MEMMAKER 386Max - MAXIMIZE Please refer to the memory managers' documentation for more information. 7.2 Problems Detecting the Data Directory If the NUA Agents report that the Database and Configuration files can not be located, check the contents of the NADMIN.DAT file located in the AGENTS directory. The "DataLocation=" line in this file should show the full UNC pathname to the Data Directory. Example: [Options] DataLocation=\\server\[volume]\pathname -----End of Readme-----